View FM3204-STR_1372229.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

this product conforms to specifications per the terms of the ramtron ramtron international corporation standard warranty. the product has completed ramtron?s internal 1850 ramtron drive, colorado springs, co 80921 qualification testing and has reached production status (800) 545-fram, (719) 481-7000 www.ramtron.com rev. 3.1 july 2010 page 1 of 21 fm3204/16/64/256 integrated processor companion with memory features high integration device replaces multiple parts ? serial nonvolatile memory ? low voltage reset ? watchdog timer ? early power-fail warning/nmi ? two 16-bit event counters ? serial number with write-lock for security processor companion ? active-low reset output for v dd and watchdog ? programmable v dd reset trip point ? manual reset filtered and debounced ? programmable watchdog timer ? dual battery-backed event counter tracks system intrusions or other events ? comparator for early power-fail interrupt ? 64-bit programmable serial number with lock ferroelectric nonvolatile ram ? 4kb, 16kb, 64kb, and 256kb versions ? unlimited read/write endurance ? 10 year data retention ? nodelay? writes fast two-wire serial interface ? up to 1 mhz maximum bus frequency ? supports legacy timing for 100 khz & 400 khz ? device select pins for up to 4 memory devices ? companion controlled via 2-wire interface easy to use configurations ? operates from 2.7 to 5.5v ? small footprint 14-pin ?green? soic (-g) ? pin compatible with fm31xx series ? low operating current ? -40 c to +85 c operation description the fm32xx is a family of integrated devices that includes the most commonly needed functions for processor-based systems. major features include nonvolatile memory available in various sizes, low- v dd reset, watchdog timer, nonvolatile event counter, lockable 64-bit serial number area, and general purpose comparator that can be used for an early power-fail (nmi) interrupt or other purpose. the family operates from 2.7 to 5.5v. the fm32xx family is software and pinout compatible with the fm31xx family which also includes a real-time clock. the common features allow a system design that easily can be assembled with or without timekeeping by simply selecting the fm31xx or fm32xx, respectively. each fm32xx provides nonvolatile ram available in sizes including 4kb, 16kb, 64kb, and 256kb versions. fast write speed and unlimited endurance allow the memory to serve as extra ram or conventional nonvolatile storage. this memory is truly nonvolatile rather than battery backed. the processor companion includes commonly needed cpu support functions. supervisory functions include a reset output signal controlled by either a low v dd condition or a watchdog timeout. /rst goes active when v dd drops below a programmable threshold and remains active for 100 ms after v dd rises above the trip point. a programmable watchdog timer runs from 100 ms to 3 seconds. the watchdog timer is optional, but if enabled it will assert the reset signal for 100 ms if not restarted by the host before the timeout. a flag-bit indicates the source of the reset. a general-purpose comparator compares an external input pin to the onboard 1.2v reference. this is useful for generating an early warning power-fail interrupt (nmi) but can be used for any purpose. the family also includes a programmable 64-bit serial number that can be locked making it unalterable. additionally the fm32xx offers a dual event counter that tracks the number of rising or falling edges detected on dedicated input pins. the counter can optionally be battery backed and even battery operated by attaching a backup power source to the vbak pin. if vbak is connected to a battery or capacitor, then events will be counted even in the absence of v dd .
fm3204/16/64/256 rev. 3.1 july 2010 page 2 of 21 pin configuration pin name function cnt1, cnt2 event counter inputs a0, a1 device select inputs pfo early power-fail output /rst reset input/output pfi early power-fail input sda serial data scl serial clock vbak battery-backup supply vdd supply voltage vss ground ordering information base configuration memory size operating voltage reset threshold ordering part number fm32256 256kb 2.7-5.5v 2.6v, 2.9, 3.9, 4.4v fm32256-g fm3264 64kb 2.7-5.5v 2.6v, 2.9, 3.9, 4.4v fm3264-g fm3216 16kb 2.7-5.5v 2.6v, 2.9, 3.9, 4.4v fm3216-g fm3204 4kb 2.7-5.5v 2.6v, 2.9, 3.9, 4.4v fm3204-g other memory configurations may be available. please contact the factory for more information. vdd vbak scl sda vss pfo cnt1 pfi rst a0 a1 cnt2 1 2 3 4 5 6 7 14 13 12 11 10 9 8 n c n c
fm3204/16/64/256 rev. 3.1 july 2010 page 3 of 21 figure 1. block diagram pin descriptions pin name type pin description a0, a1 input device select inputs are used to address multiple memories on a serial bus. to select the device the address value on the two pins must match the corresponding bits contained in the device address. the device select pins are pulled down internally. cnt1, cnt2 input event counter inputs: these battery-backed inputs increment counters when an edge is detected on the corresponding cnt pin. the polarity is programmable. these pins should not be left floating. tie to ground if pins are not used. pfo output power fail output: this is the early power-fail output. /rst i/o active low reset output with weak pull-up. also input for manual reset. sda i/o serial data & address: this is a bi-directional line for the two-wire interface. it is open-drain and is intended to be wire-or?d with other devices on the two-wire bus. the input buffer incorporates a schmitt trigger for noise immunity and the output driver includes slope control for falling edges. a pull-up resistor is required. scl input serial clock: the serial clock line for the two-wire interface. data is clocked out of the part on the falling edge, and in on the rising edge. the scl input also incorporates a schmitt trigger input for noise immunity. pfi input early power-fail input: typically connected to an unregulated power supply to detect an early power failure. this pin should not be left floating. vbak supply backup supply voltage: a 3v battery or a large value capacitor. if v dd <3.6v and no backup supply is used, this pin should be tied to v dd . if v dd >3.6v and no backup supply is used, this pin should be left floating and the vbc bit should be set. vdd supply supply voltage. vss supply ground fram array 2-wire interface scl sda rst a1, a0 pfo pfi vdd vbak 2.5v - + event counters cnt1 cnt2 special function registers s/n lockout lockout + - 1.2v watchdog lv detect switched power battery backed nonvolatile
fm3204/16/64/256 rev. 3.1 july 2010 page 4 of 21 overview the fm32xx family combines a serial nonvolatile ram with a processor companion. the companion is a highly integrated peripheral including a processor supervisor, a comparator used for early power-fail warning, nonvolatile event counters, and a 64-bit serial number. the fm32xx integrates these complementary but distinct functions that share a common interface in a single package. although monolithic, the product is organized as two logical devices, the fram memory and the companion. from the system perspective they appear to be two separate devices with unique ids on the serial bus. the fm32xx provides the same functions as the fm31xx with the exception of the real-time clock. this makes it easy to develop a common design that can either include timekeeping by using the fm31xx or exclude it by using the fm32xx. all other features are identical. the register address map is even preserved so that software can be identical. the memory is organized as a stand-alone 2-wire nonvolatile memory with a standard device id value. the companion functions are accessed under their own 2-wire device id. this allows the companion functions to be read while maintaining the most recently used memory address. the companion functions are controlled by 16 special function registers. the event counter circuits and related registers are maintained by the power source on the vbak pin, allowing them to operate from battery or backup capacitor power when v dd drops below a set threshold. each functional block is described below. memory operation the fm32xx is a family of products available in different memory sizes including 4kb, 16kb, 64kb, and 256kb. the family is software compatible, all versions use consistent two-byte addressing for the memory device. this makes the lowest density device different from its stand-alone memory counterparts but makes them compatible within the entire family. memory is organized in bytes, for example the 4kb memory is 512 x 8 and the 256kb memory is 32,768 x 8. the memory is based on fram technology. therefore it can be treated as ram and is read or written at the speed of the two-wire bus with no delays for write operations. it also offers effectively unlimited write endurance unlike other nonvolatile memory technologies. the 2-wire interface protocol is described further on page 13. the memory array can be write-protected by software. two bits in the processor companion area (wp0, wp1 in register 0bh) control the protection setting as shown in the following table. based on the setting, the protected addresses cannot be written and the 2-wire interface will not acknowledge any data to protected addresses. the special function registers containing these bits are described in detail below. write protect addresses wp1 wp0 none 0 0 bottom 1/4 0 1 bottom 1/2 1 0 full array 1 1 processor companion in addition to nonvolatile ram, the fm32xx family incorporates a highly integrated processor companion. it includes a low voltage reset, a programmable watchdog timer, battery-backed event counters, a comparator for early power-fail detection or other purposes, and a 64-bit serial number. processor supervisor supervisors provide a host processor two basic functions: detection of power supply fault conditions and a watchdog timer to escape a software lockup condition. all fm32xx devices have a reset pin (/rst) to drive the processor reset input during power faults (and power-up) and software lockups. it is an open drain output with a weak internal pull-up to v dd . this allows other reset sources to be wire- or?d to the /rst pin. when v dd is above the programmed trip point, /rst output is pulled weakly to v dd . if v dd drops below the reset trip point voltage level (v tp ) the /rst pin will be driven low. it will remain low until v dd falls too low for circuit operation which is the v rst level. when v dd rises again above v tp , /rst will continue to drive low for at least 100 ms (t rpu ) to ensure a robust system reset at a reliable v dd level. after t rpu has been met, the /rst pin will return to the weak high state. while /rst is asserted, serial bus activity is locked out even if a transaction occurred as v dd dropped below v tp . a memory operation started while v dd is above v tp will be completed internally. figure 2 below illustrates the reset operation in response to the v dd voltage. figure 2. low voltage reset vdd vtp t rpu rst
fm3204/16/64/256 rev. 3.1 july 2010 page 5 of 21 the bits vtp1 and vtp0 control the trip point of the low voltage detect circuit. they are located in register 0bh, bits 1 and 0. v tp vtp1 vtp0 2.6v 0 0 2.9v 0 1 3.9v 1 0 4.4v 1 1 the watchdog timer can also be used to assert the reset signal (/rst). the watchdog is a free running programmable timer. the period can be software programmed from 100 ms to 3 seconds in 100 ms increments via a 5-bit nonvolatile register. all programmed settings are minimum values and vary with temperature according to the operating specifications. the watchdog has two additional controls associated with its operation, a watchdog enable bit (wde) and timer restart bits (wr). both the enable bit must be set and the watchdog must timeout in order to drive /rst active. if a reset event occurs, the timer will automatically restart on the rising edge of the reset pulse. if not enabled, the watchdog timer runs but has no effect on /rst. note that setting the maximum timeout setting (11111b) disables the counter to save power. the second control is a nibble that restarts the timer preventing a reset. the timer should be restarted after changing the timeout value. the watchdog timeout value is located in register 0ah, bits 4-0, and the watchdog enable is bit 7. the watchdog is restarted by writing the pattern 1010b to the lower nibble of register 09h. writing this pattern will also cause the timer to load new timeout values. writing other patterns to this address will not affect its operation. note the watchdog timer is free- running. prior to enabling it, users should restart the timer as described above. this assures that the full timeout period will be set immediately after enabling. the watchdog is disabled when v dd is below v tp . the following table summarizes the watchdog bits. a block diagram follows. watchdog timeout wdt4-0 0ah, bits 4-0 watchdog enable wde 0ah, bit 7 watchdog restart wr3-0 09h, bits 3-0 figure 3. watchdog timer manual reset the /rst pin is bi-directional and allows the fm32xx to filter and de-bounce a manual reset switch. the /rst input detects an external low condition and responds by driving the /rst signal low for 100 ms. figure 4. manual reset note that an internal weak pull-up on /rst eliminates the need for additional external components. reset flags in case of a reset condition, a flag will be set to indicate the source of the reset. a low v dd reset is indicated by the por flag, register 09h bit 6. a watchdog reset is indicated by the wtr flag, register 09h bit 7. note that the flags are internally set in response to reset sources, but they must be cleared by the user. when the register is read, it is possible that both flags are set if both have occurred since the user last cleared them. early power fail comparator an early power fail warning can be provided to the processor well before v dd drops out of spec. the comparator is used to create a power fail interrupt (nmi). this can be accomplished by connecting the pfi pin to the unregulated power supply via a resistor divider. an application circuit is shown below. figure 5. comparator as early power-fail warning + - 1.2v ref regulato r vdd fm32xx to mcu nmi input cal/pfo pfi timebase counter watchdog timeout 100 ms clock wde /rst wr3-0 = 1010b to restart fm32xx reset switch rst mcu switch behavio r rst fm32xx drives 100 ms
fm3204/16/64/256 rev. 3.1 july 2010 page 6 of 21 the voltage on the pfi input pin is compared to an onboard 1.2v reference. when the pfi input voltage drops below this threshold, the comparator will drive the pfo pin to a low state. the comparator has 100 mv (max) of hysteresis to reduce noise sensitivity, only for a rising pfi signal. for a falling pfi edge, there is no hysteresis. the comparator is a general purpose device and its application is not limited to the nmi function. note: the maximum voltage on the comparator input pfi is limited to 3.75v under normal operating conditions. event counter the fm32xx offers the user two battery-backed event counters. input pins cnt1 and cnt2 are programmable edge detectors. each clocks a 16-bit counter. when an edge occurs, the counters will increment their respective registers. counter 1 is located in registers 0dh and 0eh, counter 2 is located in registers 0fh and 10h. these register values can be read anytime v dd is above v tp , and they will be incremented as long as a valid vbak power source is provided. to read, set the rc bit register 0ch bit 3 to 1. this takes a snapshot of all four counter bytes allowing a stable value even if a count occurs during the read. the registers can be written by software allowing the counters to be cleared or initialized by the system. counts are blocked during a write operation. the two counters can be cascaded to create a single 32-bit counter by setting the cc control bit (register 0ch). when cascaded, the cnt1 input will cause the counter to increment. cnt2 is not used in this mode. figure 6. event counter the control bits for event counting are located in register 0ch. counter 1 polarity is bit c1p, bit 0; counter 2 polarity is c2p, bit 1; the cascade control is cc, bit 2; and the read counter bit is rc bit 3. the polarity bits must be set prior to setting the counter value(s). if a polarity bit is changed, the counter may inadvertently increment. if the counter pins are not being used, tie them to ground. serial number a memory location to write a 64-bit serial number is provided. it is a writeable nonvolatile memory block that can be locked by the user once the serial number is set. the 8 bytes of data and the lock bit are all accessed via the device id for the processor companion. therefore the serial number area is separate and distinct from the memory array. the serial number registers can be written an unlimited number of times, so these locations are general purpose memory. however once the lock bit is set the values cannot be altered and the lock cannot be removed. once locked the serial number registers can still be read by the system. the serial number is located in registers 11h to 18h. the lock bit is snl, register 0bh bit 7. setting the snl bit to a 1 disables writes to the serial number registers, and the snl bit cannot be cleared . backup power the event counter and battery-backed registers may be powered with a backup power source. when the primary system power fails, the voltage on the v dd pin will drop. when v dd is less than 2.5v, the event counters and battery-backed registers will switch to the backup power supply on v bak . trickle charger to facilitate capacitor backup the v bak pin can optionally provide a trickle charge current. when the vbc bit, register 0bh bit 2, is set to 1 the v bak pin will source approximately 15 a until v bak reaches v dd or 3.75v whichever is less. in 3v systems, this charges the capacitor to v dd without an external diode and resistor charger. in 5v systems, it provides the same convenience and also prevents the user from exceeding the v bak maximum voltage specification. in the case where no battery is used, the v bak pin should be tied according to the following conditions: ? for 3.3v systems, v bak should be tied to v dd . this assumes v dd does not exceed 3.75v. ? for 5v systems, attach a 1 f capacitor to v bak and turn the trickle charger on. the v bak pin will charge to the internal backup voltage which regulates itself to about 3.6v. v bak should not be tied to 5v since the v bak (max) specification will be exceeded. a 1 f capacitor will keep the companion functions working for about 1.5 second. 16-bit counte r cnt1 cc cnt2 c1p c2p 16-bit counte r
fm3204/16/64/256 rev. 3.1 july 2010 page 7 of 21 although v bak may be connected to v ss , this is not recommended if the companion is used. none of the companion functions will operate below about 2.5v. , , , , note: systems using lithium batteries should clear the vbc bit to 0 to prevent battery charging. the v bak circuitry includes an internal 1 k ? series resistor as a safety element. register map the processor companion functions are accessed via 16 special function registers that are mapped to a separate 2- wire device id. the interface protocol is described below. the registers contain control bits, or information flags. a description of each register follows. register map summary table nonvolatile = battery-backed = data address d7 d6 d5 d4 d3 d2 d1 d0 function range serial number b y te 7 serial number 7 ffh serial number b y te 6 serial number 6 ffh serial number byte 5 serial number 5 ffh serial number b y te 4 serial number 4 ffh serial number b y te 3 serial number 3 ffh serial number b y te 2 serial number 2 ffh serial number b y te 1 serial number 1 ffh serial number byte 0 serial number 0 ffh 10h counter 2 msb event counter 2 msb ffh 0fh counter 2 lsb event counter 2 lsb ffh 0eh counter 1 msb event counter 1 msb ffh 0dh counter 1 lsb event counter 1 lsb ffh 0ch - - - - rc cc c2p c1p event count control 0bh snl - - wp1 wp0 vbc vtp1 vtp0 companion control 0ah wde - - wdt4 wdt3 wdt2 wdt1 wdt0 watchdog control 09h wtr por lb - wr3 wr2 wr1 wr0 watchdo g restart/fla g s 00-08h reserved do not use 18h 17h 11h 16h 15h 14h 13h 12h *note that the usable address range starts at address 09h to preserve software compatibility with the fm31xx device family, which includes a real-time clock in registers 00-08h. note: when the device is first powered up and programmed, all registers must be written because the battery- backed register values cannot be guaranteed. the table below shows the default values of the non-volatile registers. all other register values should be treated as unknown. default register values address hex value 18h 0x00 17h 0x00 16h 0x00 15h 0x00 14h 0x00 13h 0x00 12h 0x00 11h 0x00 0bh 0x00 0ah 0x1f
fm3204/16/64/256 rev. 3.1 july 2010 page 8 of 21 register description address description 18h serial number byte 7 d7 d6 d5 d4 d3 d2 d1 d0 sn.63 sn.62 sn.61 sn.60 sn.59 sn.58 sn.57 sn.56 upper byte of the serial number. read/write when snl=0, read-only when snl=1. nonvolatile. 17h serial number byte 6 d7 d6 d5 d4 d3 d2 d1 d0 sn.55 sn.54 sn.53 sn.52 sn.51 sn.50 sn.49 sn.48 byte 6 of the serial number. read/write when snl=0, read-only when snl=1. nonvolatile. 16h serial number byte 5 d7 d6 d5 d4 d3 d2 d1 d0 sn.47 sn.46 sn.45 sn.44 sn.43 sn.42 sn.41 sn.40 byte 5 of the serial number. read/write when snl=0, read-only when snl=1. nonvolatile. 15h serial number byte 4 d7 d6 d5 d4 d3 d2 d1 d0 sn.39 sn.38 sn.37 sn.36 sn.35 sn.34 sn.33 sn.32 byte 4 of the serial number. read/write when snl=0, read-only when snl=1. nonvolatile. 14h serial number byte 3 d7 d6 d5 d4 d3 d2 d1 d0 sn.31 sn.30 sn.29 sn.28 sn.27 sn.26 sn.25 sn.24 byte 3 of the serial number. read/write when snl=0, read-only when snl=1. nonvolatile. 13h serial number byte 2 d7 d6 d5 d4 d3 d2 d1 d0 sn.23 sn.22 sn.21 sn.20 sn.19 sn.18 sn.17 sn.16 byte 2 of the serial number. read/write when snl=0, read-only when snl=1. nonvolatile. 12h serial number byte 1 d7 d6 d5 d4 d3 d2 d1 d0 sn.15 sn.14 sn.13 sn.12 sn.11 sn.10 sn.9 sn.8 byte 1 of the serial number. read/write when snl=0, read-only when snl=1. nonvolatile. 11h serial number byte 0 d7 d6 d5 d4 d3 d2 d1 d0 sn.7 sn.6 sn.5 sn.4 sn.3 sn.2 sn.1 sn.0 lsb of the serial number. read/write when snl=0, read-only when snl=1. nonvolatile. 10h counter 2 msb d7 d6 d5 d4 d3 d2 d1 d0 c2.15 c2.14 c2.13 c2.12 c2.11 c2.10 c2.9 c2.8 event counter 2 msb. increments on overflows from counter 2 lsb. battery-backed, read/write. 0fh counter 2 lsb d7 d6 d5 d4 d3 d2 d1 d0 c2.7 c2.6 c2.5 c2.4 c2.3 c2.2 c2.1 c2.0 event counter 2 lsb. increments on programmed edge event on cnt2 input or overflows from counter 1 msb when cc=1. battery-backed, read/write . 0eh counter 1 msb d7 d6 d5 d4 d3 d2 d1 d0 c1.15 c1.14 c1.13 c1.12 c1.11 c1.10 c1.9 c1.8 event counter 1 msb. increments on overflows from counter 1 lsb. battery-backed, read/write. 0dh counter 1 lsb d7 d6 d5 d4 d3 d2 d1 d0 c1.7 c1.6 c1.5 c1.4 c1.3 c1.2 c1.1 c1.0 event counter 1 lsb. increments on programmed edge event on cnt1 input. battery-backed, read/write.
fm3204/16/64/256 rev. 3.1 july 2010 page 9 of 21 0ch event counter control d7 d6 d5 d4 d3 d2 d1 d0 - - - - rc cc c2p c1p rc read counter. setting this bit to 1 takes a snapshot of the four counters bytes allowing the system to read the values without missing count events. the rc bit will be automatically cleared. cc counter cascade. when cc=0, the event counters operate independently according to the edge programmed by c1p and c2p respectively. when cc=1, the counters are cascaded to create one 32-bit counter. the registers of counter 2 represent the most significant 16-bits of the counter and cnt1 is the controlling input. bit c2p is ?don?t care? when cc=1. battery-backed, read/write. c2p cnt2 detects falling edges when c2p = 0, rising edges when c2p = 1. c2p is ?don?t care? when cc=1. the value of event counter 2 may inadvertently increment if c2p is changed. battery-backed, read/write. c1p cnt1 detects falling edges when c1p = 0, rising edges when c1p = 1. the value of event counter 1 may inadvertently increment if c1p is changed. battery-backed, read/write. 0bh companion control d7 d6 d5 d4 d3 d2 d1 d0 snl - - wp1 wp0 vbc vtp1 vtp0 snl serial number lock. setting to a 1 makes registers 11h to 18h and snl permanently read-only. snl cannot be cleared once set to 1. nonvolatile, read/write. wp1-0 write protect. these bits control the write protection of the memory array. nonvolatile, read/write. write protect addresses wp1 wp0 none 0 0 bottom 1/4 0 1 bottom 1/2 1 0 full array 1 1 vbc vbak charger control. setting vbc to 1 causes a 15 a trickle charge current to be supplied on vbak. clearing vbc to 0 disables the charge current. nonvolatile, read/write. vtp1-0 vtp select. these bits control the reset trip point for the low v dd reset function. nonvolatile, read/write. vtp vtp1 vtp0 2.6v 0 0 2.9v 0 1 3.9v 1 0 4.4v 1 1 0ah watchdog control d7 d6 d5 d4 d3 d2 d1 d0 wde - - wdt4 wdt3 wdt2 wdt1 wdt0 wde watchdog enable. when wde=1 the watchdog timer can cause the /rst signal to go active. when wde = 0 the timer runs but has no effect on /rst. note as the timer is free-running, users should restart the timer using wr3-0 prior to setting wde=1. this assures a full watchdog timeout interval occurs. nonvolatile, read/write. wdt4-0 watchdog timeout. indicates the minimum watchdog timeout interval with 100 ms resolution. new watchdog timeouts are loaded when the timer is restarted by writing the 1010b pattern to wr3-0. nonvolatile, read/write. watchdog timeout wdt4 wdt3 wdt2 wdt1 wdt0 invalid ? default 100 ms 0 0 0 0 0 100 ms 0 0 0 0 1 200 ms 0 0 0 1 0 300 ms 0 0 0 1 1 . . . 2000 ms 1 0 1 0 0 2100 ms 1 0 1 0 1 2200 ms 1 0 1 1 0 . . . 2900 ms 1 1 1 0 1 3000 ms 1 1 1 1 0 disable counter 1 1 1 1 1
fm3204/16/64/256 rev. 3.1 july 2010 page 10 of 21 09h watchdog restart & flags d7 d6 d5 d4 d3 d2 d1 d0 wtr por lb - wr3 wr2 wr1 wr0 wtr watchdog timer reset flag: when the /rst signal is activated by the watchdog the wtr bit will be set to 1. it must be cleared by the user. note that both wtr and por could be set if both reset sources have occurred since the flags were cleared by the user. battery-backed. read/write (internally set, user can clear bit). por power-on reset flag: when the /rst pin is activated by v dd < v tp , the por bit will be set to 1. it must be cleared by the user. note that both wtr and por could be set if both reset sources have occurred since the flags were cleared by the user. battery-backed. read/write (internally set, user can clear bit). lb low backup flag: on power up, if the vbak source is below the minimum voltage to operate the event counters, this bit will be set to 1. the user should clear it to 0 when initializing the system. battery-backed. read/write (internally set, user can clear bit). wr3-0 watchdog restart: writing a pattern 1010b to wr3-0 restarts the watchdog timer. the upper nibble contents do not affect this operation. writing any pattern other than 1010b to wr3-0 has no effect on the timer. this allows users to clear the wtr, por, and lb flags without affecting the watchdog timer. write-only. 00-08h reserved ? do not use this address space
fm3204/16/64/256 rev. 3.1 july 2010 page 11 of 21 two-wire interface the fm32xx employs an industry standard two-wire bus that is familiar to many users. this product is unique since it incorporates two logical devices in one chip. each logical device can be accessed individually. although monolithic, it appears to the system software to be two separate products. one is a memory device. it has a slave address (slave id = 1010b) that operates the same as a stand-alone memory device. the second device is a real-time clock and processor companion which have a unique slave address (slave id = 1101b). by convention, any device that is sending data onto the bus is the transmitter while the target device for this data is the receiver. the device that is controlling the bus is the master. the master is responsible for generating the clock signal for all operations. any device on the bus that is being controlled is a slave. the fm32xx is always a slave device. the bus protocol is controlled by transition states in the sda and scl signals. there are four conditions: start, stop, data bit, and acknowledge. the figure below illustrates the signal conditions that specify the four states. detailed timing diagrams are shown in the electrical specifications section. stop (master) start (master) 7 data bits (transmitter) 6 0 data bit (transmitter) acknowledge (receiver) scl sda figure 7. data transfer protocol start condition a start condition is indicated when the bus master drives sda from high to low while the scl signal is high. all read and write transactions begin with a start condition. an operation in progress can be aborted by asserting a start condition at any time. aborting an operation using the start condition will ready the fm32xx for a new operation. if the power supply drops below the specified v tp during operation, any 2-wire transaction in progress will be aborted and the system must issue a start condition prior to performing another operation. stop condition a stop condition is indicated when the bus master drives sda from low to high while the scl signal is high. all operations must end with a stop condition. if an operation is pending when a stop is asserted, the operation will be aborted. the master must have control of sda (not a memory read) in order to assert a stop condition. data/address transfer all data transfers (including addresses) take place while the scl signal is high. except under the two conditions described above, the sda signal should not change while scl is high. acknowledge the acknowledge (ack) takes place after the 8 th data bit has been transferred in any transaction. during this state the transmitter must release the sda bus to allow the receiver to drive it. the receiver drives the sda signal low to acknowledge receipt of the byte. if the receiver does not drive sda low, the condition is a no-acknowledge (nack) and the operation is aborted. the receiver might nack for two distinct reasons. first is that a byte transfer fails. in this case, the nack ends the current operation so that the part can be addressed again. this allows the last byte to be recovered in the event of a communication error. second and most common, the receiver does not send an ack to deliberately terminate an operation. for example, during a read operation, the fm32xx will continue to place data onto the bus as long as the receiver sends acks (and clocks). when a read operation is complete and no more data is needed, the receiver must nack the last byte. if the receiver acks the last byte, this will cause the fm32xx to attempt to drive the bus on the next clock while the master is sending a new command such as a stop.
fm3204/16/64/256 rev. 3.1 july 2010 page 12 of 21 slave address the first byte that the fm32xx expects after a start condition is the slave address. as shown in figures below, the slave address contains the slave id, device select address, and a bit that specifies if the transaction is a read or a write. the fm32xx has two slave addresses (slave ids) associated with two logical devices. to access the memory device, bits 7-4 should be set to 1010b. the other logical device within the fm32xx is the real- time clock and companion. to access this device, bits 7-4 of the slave address should be set to 1101b. a bus transaction with this slave address will not affect the memory in any way. the figures below illustrate the two slave addresses. the device select bits allow multiple devices of the same type to reside on the 2-wire bus. the device select bits (bits 2-1) select one of four parts on a two- wire bus. they must match the corresponding value on the external address pins in order to select the device. bit 0 is the read/write bit. a ?1? indicates a read operation, and a ?0? indicates a write operation. 1 0 1 0 x a1a0r/w slave id device select 76543 21 0 figure 8. slave address - memory figure 9. slave address ? companion addressing overview ? memory after the fm32xx acknowledges the slave address, the master can place the memory address on the bus for a write operation. the address requires two bytes. this is true for all members of the family. therefore the 4kb and 16kb configurations will be addressed differently from stand alone serial memories but the entire family will be upwardly compatible with no software changes. the first is the msb (upper byte). for a given density unused address bits are don?t cares, but should be set to 0 to maintain upward compatibility. following the msb is the lsb (lower byte) which contains the remaining eight address bits. the address is latched internally. each access causes the latched address to be incremented automatically. the current address is the value that is held in the latch, either a newly written value or the address following the last access. the current address will be held as long as v dd > v tp or until a new value is written. accesses to the clock do not affect the current memory address. reads always use the current address. a random read address can be loaded by beginning a write operation as explained below. after transmission of each data byte, just prior to the acknowledge, the fm32xx increments the internal address. this allows the next sequential byte to be accessed with no additional addressing externally. after the last address is reached, the address latch will roll over to 0000h. there is no limit to the number of bytes that can be accessed with a single read or write operation. addressing overview ? companion the processor companion operate in a similar manner to the memory, except that it uses only one byte of address. addresses 00h to 18h correspond to special function registers. attempting to load addresses above 18h is an illegal condition; the fm32xx will return a nack and abort the 2-wire transaction. data transfer after the address information has been transmitted, data transfer between the bus master and the fm32xx begins. for a read, the fm32xx will place 8 data bits on the bus then wait for an ack from the master. if the ack occurs, the fm32xx will transfer the next byte. if the ack is not sent, the fm32xx will end the read operation. for a write operation, the fm32xx will accept 8 data bits from the master then send an acknowledge. all data transfer occurs msb (most significant bit) first. memory write operation all memory writes begin with a slave address, then a memory address. the bus master indicates a write operation by setting the slave address lsb to a 0. after addressing, the bus master sends each byte of data to the memory and the memory generates an acknowledge condition. any number of sequential bytes may be written. if the end of the address range is reached internally, the address counter will wrap to 0000h. internally, the actual memory write occurs after the 8 th data bit is transferred. it will be complete before the acknowledge is sent. therefore, if the user desires to abort a write without altering the memory contents, this should be done using a start 11 0 1 x a 1 a 0r/w slave id 76543 21 0 device select
fm3204/16/64/256 rev. 3.1 july 2010 page 13 of 21 or stop condition prior to the 8 th data bit. the figures below illustrate a single- and multiple-writes to memory. figure 10. single byte memory write figure 11. multiple byte memory write memory read operation there are two types of memory read operations. they are current address read and selective address read. in a current address read, the fm32xx uses the internal address latch to supply the address. in a selective read, the user performs a procedure to first set the address to a specific value. current address & sequential read as mentioned above the fm32xx uses an internal latch to supply the address for a read operation. a current address read uses the existing value in the address latch as a starting place for the read operation. the system reads from the address immediately following that of the last operation. to perform a current address read, the bus master supplies a slave address with the lsb set to 1. this indicates that a read operation is requested. after receiving the complete device address, the fm32xx will begin shifting data out from the current address on the next clock. the current address is the value held in the internal address latch. beginning with the current address, the bus master can read any number of bytes. thus, a sequential read is simply a current address read with multiple byte transfers. after each byte the internal address counter will be incremented. each time the bus master acknowledges a byte, this indicates that the fm32xx should read out the next sequential byte. there are four ways to terminate a read operation. failing to properly terminate the read will most likely create a bus contention as the fm32xx attempts to read out additional data onto the bus. the four valid methods follow. 1. the bus master issues a nack in the 9 th clock cycle and a stop in the 10 th clock cycle. this is illustrated in the diagrams below and is preferred. 2. the bus master issues a nack in the 9 th clock cycle and a start in the 10 th . 3. the bus master issues a stop in the 9 th clock cycle. 4. the bus master issues a start in the 9 th clock cycle. if the internal address reaches the top of memory, it will wrap around to 0000h on the next read cycle. the figures below show the proper operation for current address reads. selective (random) read there is a simple technique that allows a user to select a random address location as the starting point for a read operation. this involves using the first s a slave address 0 address msb a data byte a p by master by fm32xx star t address & data stop acknowledge address lsb a data byte a s a slave address 0 address msb a data byte a p by master by fm32xx start a ddress & data stop a cknowledge a ddress lsb a
fm3204/16/64/256 rev. 3.1 july 2010 page 14 of 21 three bytes of a write operation to set the internal address followed by subsequent read operations. to perform a selective read, the bus master sends out the slave address with the lsb set to 0. this specifies a write operation. according to the write protocol, the bus master then sends the address bytes that are loaded into the internal address latch. after the fm32xx acknowledges the address, the bus master issues a start condition. this simultaneously aborts the write operation and allows the read command to be issued with the slave address lsb set to a 1. the operation is now a read from the current address. read operations are illustrated below. companion write operation all companion writes operate in a similar manner to memory writes. the distinction is that a different device id is used and only one byte of address is needed instead of two. figure 15 illustrates a single byte write to this device. companion read operation as with writes, a read operation begins with the slave address. to perform a register read, the bus master supplies a slave address with the lsb set to 1. this indicates that a read operation is requested. after receiving the complete slave address, the fm32xx will begin shifting data out from the current register address on the next clock. auto-increment operates for the special function registers as with the memory address. a current address read for the registers look exactly like the memory except that the device id is different. the fm32xx contains two separate address registers, one for the memory address and the other for the register address. this allows the contents of one address register to be modified without affecting the current address of the other register. for example, this would allow an interrupted read to the memory while still providing fast access to a companion register. a subsequent memory read will then continue from the memory address where it previously left off, without requiring the load of a new memory address. however, a write sequence always requires an address to be supplied. figure 12. current address memory read figure 13. sequential memory read s a slave address 1 data byte 1 p by maste r by fm32xx start address stop acknowledge no acknowledge data s a slave address 1 data byte 1 p by maste r by fm32xx star t a ddress stop a cknowledge no a cknowledge data data byte a a cknowledge
fm3204/16/64/256 rev. 3.1 july 2010 page 15 of 21 figure 14. selective (random) memory read figure 15. byte register write * although not required, it is recommended that a5-a7 in the register address byte are zeros in order to preserve compatibility with future devices. addressing fram array in the fm32xx family the fm32xx family includes 256kb, 64kb, 16kb, and 4kb memory densities. the following 2-byte address field is shown for each density. table 4. two-byte memory address part # 1 s t address byte 2 n d address byte fm32256 x a14 a13 a12 a11 a10 a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 fm3264 x x x a12 a11 a10 a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 fm3216 x x x x x a10 a9 a8 a7 a6 a5 a4 a3 a2 a1 a0 fm3204 x x x x x x x a8 a7 a6 a5 a4 a3 a2 a1 a0 s a slave address 0 address a data byte a p by maste r start address & data stop acknowledge 000 by fm32xx s a slave address 1 data byte 1 p by master by fm32xx star t address stop no acknowledge data s a slave address 0 address msb a start address acknowledge address lsb a
fm3204/16/64/256 rev. 3.1 july 2010 page 16 of 21 electrical specifications absolute maximum ratings symbol description ratings v dd power supply voltage with respect to v ss -1.0v to +7.0v v in voltage on any signal pin with respect to v ss -1.0v to +7.0v * and v in v dd +1.0v ** v bak backup supply voltage -1.0v to +4.5v t stg storage temperature -55 c to + 125 c t lead lead temperature (soldering, 10 seconds) 260 c v esd electrostatic discharge voltage - human body model (jedec std jesd22-a114-b) - charged device model (jedec std jesd22-c101-a) - machine model (jedec std jesd22-a115-a) 4kv 1kv 250v package moisture sensitivity level msl-1 * pfi input voltage must not exceed 4.5v. ** the ?v in < v dd +1.0v? restriction does not apply to the scl and sda inputs which do not employ a diode to v dd . stresses above those listed under absolute maximum ratings may cause permanent damage to the device. this is a stress rating on ly, and the functional operation of the device at these or any other conditions above those listed in the operational section of th is specification is not implied. exposure to absolute maximum ratings conditions for extended periods may affect device reliabilit y. dc operating conditions ( t a = -40 c to + 85 c, v dd = 2.7v to 5.5v unless otherwise specified) symbol parameter min typ max units notes v dd main power supply 2.7 5.5 v 7 i dd v dd supply current @ scl = 100 khz @ scl = 400 khz @ scl = 1 mhz 500 900 1500 a a a 1 i sb standby current for v dd < 5.5v for v dd < 3.6v 150 120 a a 2 v bak backup supply voltage 2.0 3.0 3.75 v 9 i bak backup supply current 1 1 1 ?
fm3204/16/64/256 rev. 3.1 july 2010 page 17 of 21 continued ? dc operating conditions, continued (t a = -40 c to + 85 c, v dd = 2.7v to 5.5v unless otherwise specified) symbol parameter min typ max units notes r in input resistance (pulldown) a1-a0 for v in = v il max a1-a0 for v in = v ih min 20 1 k ? m ? v pfi power fail input reference voltage 1.175 1.20 1.225 v v hys power fail input (pfi) hysteresis (rising) - 100 mv notes 1. scl toggling between v dd -0.3v and v ss , other inputs v ss or v dd -0.3v. 2. all inputs at v ss or v dd, static. stop command issued. 3. v in or v out = v ss to v dd . does not apply to a0, a1, pfi, or /rst pins. 4. v bak = 3.0v, v dd < 2.4v, cnt1-2 at v bak . 5. /rst is asserted low when v dd < v tp . 6. the minimum v dd to guarantee the level of /rst remains a valid v ol level. 7. full complete operation. supervisory circuits operate to lower voltages as specified. 8. includes /rst input detection of external reset condition to trigger driving of /rst signal by fm32xx. 9. the vbak trickle charger automatically regulates the maximum voltage on this pin for capacitor backup applications. 10. v bak will source current when trickle charge is enabled (vbc bit=1), v dd > v bak , and v bak < v bak max. ac parameters (t a = -40 c to + 85 c, v dd = 2.7v to 5.5v, c l = 100 pf unless otherwise specified) symbol parameter min max min max min max units notes f scl scl clock frequency 0 100 0 400 0 1000 khz t low clock low period 4.7 1.3 0.6 capacitance (t a = 25 c, f=1.0 mhz, v dd = 3.0v) symbol parameter typ max units notes c io input/output capacitance - 8 pf 1 notes 1 this parameter is characterized but not tested. data retention (t a = -40 c to + 85 c, v dd = 2.7v to 5.5v) parameter min units notes data retention 10 years
fm3204/16/64/256 rev. 3.1 july 2010 page 18 of 21 supervisor timing (t a = -40 c to + 85 c, v dd = 2.7v to 5.5v) symbol parameter min max units notes t rpu /rst active (low) after v dd >v tp 100 200 ms t rnr v dd < v tp noise immunity 10 25 notes 1 this parameter is characterized but not tested. 2 slope measured at any point on v dd waveform. 3 t dog is the programmed time in register 0ah, v dd > v tp and t rpu satisfied. /rst timing vdd vtp vrst rst t rpu t rnr
fm3204/16/64/256 rev. 3.1 july 2010 page 19 of 21 ac test conditions equivalent ac load circuit input pulse levels 0.1 v dd to 0.9 v dd input rise and fall times 10 ns input and output timing levels 0.5 v dd diagram notes all start and stop timing parameters apply to both read and write cycles. clock specifications are identical for read and write cycles. write timing parameters apply to slave address, word address, and write data bits. functional relationships are illustrated in the relevant data sheet sections. these diagrams illustrate the timing parameters only. read bus timing t su:sta start t r ` t f stop start t buf t high 1/f scl t low t sp t sp acknowledge t hd:dat t su:dat t aa t dh scl sda write bus timing t su:sto start stop start acknowledge t aa t hd:dat t hd:sta t su:dat scl sda 5.5v output 1700 ? 100 pf
fm3204/16/64/256 rev. 3.1 july 2010 page 20 of 21 mechanical drawing 14-pin soic (jedec standard ms-012 variation ab) refer to jedec ms-012 for complete dimensions and notes. all dimensions in millimeters . soic package marking scheme legend: xxxx= part number, p= package type (-g) lllllll= lot code ric=ramtron int?l corp, yy=year, ww=work week example: fm32256, ?green? soic package, year 2009, work week 42 fm32256-g b90007g ric 0942 xxxxxxx-p lllllll ric yyww
fm3204/16/64/256 rev. 3.1 july 2010 page 21 of 21 revision history revision date summary 0.2 5/22/03 initial release. 0.21 11/25/03 fixed package drawing dimensions. 1.0 3/30/04 changed product status to preliminary. added v tp and v pfi parameters in dc operating table. changed v hys limits. added ?green? package. 2.0 10/25/04 changed to pre-production status. added text to trickle charger section. improved spec limits on v tp , v pfi , and v hys parameters and changed v ih max limits in dc operating table. added companion register table with default values. added package marking scheme and board footprint. devices marked with date codes 0440 and higher comply with the revision of the datasheet. 2.1 12/8/04 changed description of por flag and manual reset (pg. 5, 10). added notes to absolute maximum ratings. 2.2 10/5/05 rewrote section on battery backup. added comment about unused cnt pins. 2.3 10/2/06 removed -s packaging option which is not recommended for new designs. added esd and msl ratings which are valid for date codes 0440 and higher. 2.4 3/18/2008 not recommended for new designs. as an alternative, use fm3127xb for 5v designs or fm31l27xb for 3v designs. 3.0 3/30/2010 changed to production status. these products are no longer not recommended for new designs (nrnd). updated esd ratings. updated lead temperature rating in abs max table. removed battery insertion sequence text (p. 6). the sequence is no longer necessary for devices with date codes after 0701. 3.1 7/27/2010 removed text indicating that a manual reset sets the por flag.

▲Up To Search▲

Price & Availability of FM3204-STR

	To Download FM3204-STR Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .